From e452711ddaea84732fffdd1ac06a4131c5921328 Mon Sep 17 00:00:00 2001 From: psxvoid Date: Tue, 31 Dec 2024 06:16:08 +0000 Subject: [PATCH] Added a comment: ViFM Plugin Which Partially Solves The Issue --- .../comment_5_a1d1c2bf6e9e181f472aee8fef28795b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_5_a1d1c2bf6e9e181f472aee8fef28795b._comment diff --git a/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_5_a1d1c2bf6e9e181f472aee8fef28795b._comment b/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_5_a1d1c2bf6e9e181f472aee8fef28795b._comment new file mode 100644 index 0000000000..bda16dc55c --- /dev/null +++ b/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_5_a1d1c2bf6e9e181f472aee8fef28795b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="psxvoid" + avatar="http://cdn.libravatar.org/avatar/fde068fbdeabeea31e3be7aa9c55d84b" + subject="ViFM Plugin Which Partially Solves The Issue" + date="2024-12-31T06:16:08Z" + content=""" +I wrote a proof of concept [plugin](https://github.com/psxvoid/vifm-git-mv) for [ViFM](https://github.com/vifm/vifm) which allows to move files around and replace `mv` command for such moves with `git mv`. It partially solves the issue - git detects such moves as renames. But because git annex makes \"fixup\" for symbolic links in pre-commit hook, then git detects file change as well. A workaround to this might be separating those operations into two commits - one with rename and another one with symlink fixup. However, I wish it were possible to do this in a cleaner way. +"""]] -- 2.30.2